Fix rejected/silently-dropped request fields SDK-wide; omvs_audit Java checks; new Egeria APIs (ISSUE-163/164/165) - #483

…a source (ISSUE-164)

- RENAMED (verb+path) matches now get the verb/body checks; they were skipped,
  which hid two ISSUE-163 detach bugs.
- New Java ground truth (--java-dir / $EGERIA_JAVA_DIR, --no-java to skip):
  indexes Spring endpoints -> @RequestBody type and reports
  JAVA-BODY REJECTED (sibling class under a @JsonTypeInfo base: a 400),
  CLASS-IGNORED, UNKNOWN-CLASS (Properties/RequestBody names Egeria lacks,
  scanned in pyegeria/omvs, md_processing and commands), JAVA-MISSING and
  HTTP-vs-JAVA. A .http BODY mismatch Java contradicts no longer fails.
- Strips the 'retrieve"}' junk on some .http lines.

On the pre-ISSUE-163 code it flags all eight ISSUE-163 bugs.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…E-163's audit note

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…SSUE-164)

- FIELD-DROP: a method passes an argument whose JSON key the server-side
  class (with ancestors) does not declare; Egeria's ignoreUnknown=true
  discards it without error. Helper argument -> JSON key maps are read from
  each helper's dict literals, following local aliases; a parameter counts
  as dropped only if every key it can fill is dropped.
- CLIENT-DROP: a dict naming a pyegeria model via "class" uses a key the
  model reads neither as alias nor field name, so Pydantic drops it before
  sending.
- MODEL-FIELD gaps (review): model fields the Java class lacks, per pair,
  with the methods using it.
- Java field index honours @JsonProperty, skips statics, and excludes
  adapters/ (connector DTOs reuse API class names).

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…d1a7f1

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…164)

- NewElementRequestBody / NewRelationshipRequestBody / TemplateRequestBody:
  anchor_scope_guids now serialises as anchorScopeGUIDs (Egeria's
  MakeAnchorOptions name). The generated alias anchorScopeGuids was dropped
  by Egeria, and the documented anchorScopeGUIDs by extra='ignore', so anchor
  scope could never be set. All three spellings are still read.
- _async_find_request (every find_*): send governanceZoneFilter,
  relationshipsPageSize, anchorScopeGUID and startFrom instead of zoneFilter,
  relationshipPageSize, anchorScopeGuid and start_from, which the model
  discarded; the property-names branch now sends the zone filter too. Removed
  anchorTypeName, which no Egeria options class has.

5 micro-tests, all fail on the old code.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…ith --live results

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

Each verified against Egeria main 4486d1a7f1's Spring resources and
@JsonSubTypes registrations (registered names and aliases):
- remove_is_abstract_concept, remove_activity_description: send
  DeleteClassificationRequestBody (was an element / relationship body).
- detach_cohort_member: relationship delete; the metadata-source helper
  always sent MetadataSourceRequestBody, not a DeleteRequestBody subtype.
- remove_search_keyword: element delete, as Egeria declares.
- initiate_engine_action: InitiateEngineActionRequestBody with
  actionSourceGUIDs and startDate; requestSourceGUIDs and startTime were
  dropped, so a scheduled action started at once.
- add/remove_is_data_value default DataValueMeaningProperties;
  solution roles SolutionActorRoleProperties; GOV_DEF_PROPERTIES_LIST
  DataProcessingPurposeProperties; CLI todo update UpdateElementRequestBody
  (typo failed client-side validation).

Left alone on purpose: RetentionClassificationProperties and
SecurityGroupMembershipProperties are registered aliases.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…d classes

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…eys (ISSUE-164)

- ActionRequestBody: anchorGUID, isOwnAnchor, anchorScopeGUIDs,
  initialClassifications and newActionTargets (Egeria's names; the old
  actionTargetGUIDs key is still read). My Profile's isOwnAnchor on
  to-dos/meetings/reviews was being dropped client-side.
- TemplateRequestBody: parentRelationshipProperties added;
  initial_classifications now serialises as replacementClassifications,
  Egeria's template name for it (the old key is still read).
- Dr.Egeria set_find_body: endsWith (was endWith, ignored); set_create_body:
  anchorScopeGUIDs list (was a singular key, dropped); create/update bodies no
  longer send governanceZoneFilter, which Egeria's create/update bodies lack.
- CLI glossary actions: anchorScopeGUIDs list; update sends properties (was
  elementProperties, so the update carried no properties).

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…tadata Expert still has a classifications list

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

… product catalog

From the refreshed .http collections, checked against Egeria main 4486d1a7f1
(Spring @RequestBody types and registered properties classes):
- ClassificationExplorer: add/update/clear_usage_activity and
  add/update/clear_member_popularity_profile (New/Update/Delete classification
  bodies; UsageActivityProperties, MemberPopularityProfileProperties).
- MetadataExpert: undo_metadata_element_update, restore_metadata_element,
  undo_related_elements_update, restore_related_elements
  (MetadataSourceRequestBody; Egeria returns VoidResponse).
- New ProductCatalog client (pyegeria, EgeriaTech "product_catalog"):
  find_digital_product_catalogs on the product-catalog URL marker. It
  inherits CollectionManager without changing its root, so facade resolution
  of inherited methods is unchanged.

omvs_audit now reports 0 MISSING (was 13). 9 micro-tests.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…'t serve

Validated against Egeria main 4486d1a7f1, the live platform's OpenAPI doc,
and git history: 13 removed upstream (with removing commit), 6 never existed,
plus the Dr.Egeria command affected and proposed handling.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…; ISSUE-165 move check

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

link_subject_area_hierarchy / detach_subject_area_hierarchy called
subject-area/collections/{g}/collection-hierarchies/{g}/..., which Egeria
never served (404). SubjectAreaResource maps
subject-area/subject-areas/{parent}/subject-area-hierarchies/{nested}/...;
link_subject_areas / detach_subject_areas already used it, so these were
broken duplicates. Both names kept.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…ivity updates

UsageActivity / MemberPopularityProfile, undo/restore (element and
relationship; restore also reverses a Memento archive, keeping the GUID and
original qualifiedName), subject-area hierarchy and product-catalog find
verified on quickstart 9443. Update docstrings now say to send every count:
Egeria's counts are primitive longs, so an omitted count resets to 0 even
with mergeUpdate. Marks ISSUE-155 items 4 (partly), 5, 6 and ISSUE-159's
restore proposal.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>

…lass-names

Resolved the only conflict, PYEGERIA_ISSUES.md: both PRs inserted entries at
the top of "Open pyegeria items". Kept both, newest first: ISSUE-165, 164,
163, then 162.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>